Setup Guide Intro:
This document:
- is intended to provide recommendations and implementation guidance for integration of the Promis.e Configuration into a ProjectWise Environment.
- is intended to provide the best path to integrate Promis.e CONNECT Edition with ProjectWise CONNECT Edition.
- will focus on topics concerning ProjectWise Configuration integration and WorkSet/Project association. Please refer to ProjectWise documentation for topics not addressed.
- Acronym: CSB = Configuration Settings Block
- Terminology - "ProjectWise Managed WorkSpaces" refers to a V8i generation of a managed configuration. "ProjectWise Promis.e " refers to a CONNECT Edition generation of a managed configuration.
Restriction and Limitations integrating with ProjectWise Promis.e
- Promis.e CONNECT Edition is compatible with a ProjectWise Design Integration Server CONNECT Edition and requires a ProjectWise Explorer CONNECT Edition or later.
- ProjectWise Promis.e does not support an offline or briefcase mode. ProjectWise Promis.e s require an active connection to a ProjectWise server.
- ProjectWise Promis.e is a thick-client solution and is not supported with ProjectWise Web Parts (SharePoint Web parts).
- ProjectWise administrators and users are encouraged to set the user option to "Leave Local Copy on check in" for ProjectWise Promis.e s. This will improve operational performance for large projects. If changes in files are detected, ProjectWise will synchronize as required.
- The WorkSpace and WorkSet configuration files must be included in the ProjectWise Promis.e . Meaning, the CONFIGURATION (root)/WORKSPACENAME/WORSETNAME along with the associated configuration files must be managed in ProjectWise.
- WorkSpace and WorkSet Configuration files located in ProjectWise are automatically processed and are incorporated as part of ProjectWise Promis.e . Diligence is required to ensure the configuration files contained within ProjectWise do not contaminate the ProjectWise Promis.e .
- When working with ProjectWise Promis.e , it is recommended that users access files through the ProjectWise Explorer and not through application shortcuts in the start menu, quick launch toolbar, or desktop. These application shortcuts will open the application in an un-managed mode and require the application to restart when opening a managed file.
- The ProjectWise environment can be configured for a "Captive" environment. (When working in integrated applications, the term captive environment refers to the state of integration when the user cannot save documents to or open documents from the local file system. They are "captive" to working in the ProjectWise environment). Please consult your ProjectWise implementation team and/or administrators before configuring ProjectWise for a "Captive" environment.
- If you have an existing ProjectWise Promis.e deployments of Promis.e , please note that Promis.e datasets are not intended to be backwards compatible and should not be shared with older versions of Promis.e . Therefore, we encourage user to create a separate workspace and dataset dedicated to each version.